enrich(sudoku,#13410): prose interpretative Backtracking/Genetic/GraphColoring C# (densite 1172/842/862 -> 1286/1327/1301) - #16027

…uctural fold (#16112)

The existing organ (#15901) measures source VOLUME. A cell whose source folds
entirely into a comment is invisible to it by construction: on the founding
case (PR #16097, Lean-18 cell 40cb37d5) the head GROWS 1132 -> 1728 chars
because the same write that stripped the newlines appended a 639-char recovery
note, so the magnitude gate stops before any floor. The BLOCKING
notebook-cell-source-parses guard is blind too -- a fully commented cell parses
clean -- which is why it stayed green on a cell whose code had disappeared.

Adds two structural signals to the SAME check-run, no new fast-lane wiring:

  * `emptied`       matched cell whose statement count went from > 0 to 0.
  * `orphan-output` non-empty outputs with 0 statements and no IPython magic
                    (base-free by construction -- the issue's 3rd criterion).

The existing exemptions speak about the base->head RELATION, so they arbitrate
the comparative signal only; `orphan-output` is intra-cell and stays true
whatever happens to the code elsewhere. Both exemption fractions measure 0.00
on the founding case, so nothing was suppressed.

`_scan_line` / `_strip_ipython_magics` / `_is_python_kernel` are imported from
check_cell_source_parses rather than reimplemented, so the organs cannot
disagree about the same cell.

Criterion 1 of the issue (unterminated-item count) is REFUTED by measurement,
not implemented: per-character serialization already exists on main
(GenAI/Texte/21_LoRA_FineTuning.ipynb cell 69b296cb -> 802 unterminated items,
10 statements, real output, healthy). Histogram over the 11970 code cells of
main's 953 Python notebooks: {0: 11970, 1: 1, 802: 1}. The signal is withdrawn
rather than shipped with a threshold; the folds it targeted are covered twice
without it (code-first fold -> the blocking syntax guard; comment-first fold ->
`emptied`).

Calibration: 0 structural findings on main's full Python corpus; 0 structural
findings on the 18 notebooks changed by 12 merged PRs (#16080, #16071, #16069,
#16067, #16041, #16039, #16027, #16024, #16021, #16020, #16013, #16012). A
first sweep without the no-magic guard flagged 6 cells, all `# comment` +
`!python`/`%pip` -- the magic IS the producer, so the guard is measured
necessity, not caution.

Evidence: 30 tests green in the file, 89 across the sibling organ files;
`--self-test` OK with BOTH founding-case replays firing (volume #15901 and
structure #16110); live end-to-end run at #16097's head reports the exact
measured finding with RC=1.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

…ent C#

Le redressement P16 retire 8 cellules de prose ajoutees par la campagne de
densite sur le cote C# des 4 paires Sudoku, sans toucher les jumeaux Python.
Les blob/content sha C# derivent donc, et `Twin parity audit (#8057)`
rougissait sur 4 paires qui etaient OK au base-ref origin/main.

Audit firsthand AVANT re-baseline (un --update aveugle consecrerait une
regression) : les 8 ids de cellule supprimes n'existent que dans des commits
de campagne, aucun n'est du contenu pre-campagne.
- 7 cellules (Sudoku-01 x1, Sudoku-03 x2, Sudoku-09 x4) ajoutees par
  d28e23e du 2026-09-14 (#16027, prose interpretative C#)
- 1 cellule (Sudoku-14 x1) ajoutee par 1f32e89 du 2026-09-03 (#14368)

Cote Python : recorded_python_sha == current_python_sha sur les 4 paires,
donc le jumeau Python n'a pas bouge. Le redressement annule exactement
l'enrichissement qui avait cause la derive.

Preuve : check_twin_parity.py --check rend [OK] sur les 4 paires apres update.
Le registre ne recoit que 4 enregistrements d'audit (SHA + date + auteur),
aucun notebook n'est modifie par ce commit.

Co-Authored-By: Claude Code <noreply@anthropic.com>

… supprimees (#17051)

* fix(density,#17040): redressement paquet P16 — 8 cellules redondantes supprimees

Suppression de cellules markdown "lecture" ajoutees par la campagne #13410
qui doublonnaient une lecture pre-existante du meme output de cellule code.

Regle appliquee : (a) une sortie = AU PLUS UNE lecture, (c) SUPPRIMER les
doublons d'une lecture pre-existante. Cellules conservees intactes.

Notebooks modifies (5/12 du paquet) :
- MGS-30-ScatterSearch-Decomposition : 1 cellule (lecture du temoin)
- Sudoku-01-Backtracking-Csharp : 1 cellule (lecture 122->490304->12625368)
- Sudoku-03-Genetic-Csharp : 2 cellules (lectures MRV/GA intermediaires)
- Sudoku-09-GraphColoring-Csharp : 4 cellules (lectures SudokuGraph/MRV/DSATUR/QuikGraph)
- Sudoku-14-BDD-Csharp : 1 cellule (lecture integration BDD)

7 autres notebooks du paquet deja propres (MGS-17, MGS-20, Sudoku-06/07/11,
Argumentum I2, Lean-14b) : la campagne n'y a ajoute aucune cellule
redondante avec une lecture pre-existante.

Markdown-only : aucune re-execution requise (exception C.2). Cellules code,
outputs, execution_count et metadata intacts.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(density,#17066): Sudoku-03 interpretations dupliquees retitrees — experiences distinctes (chromosome par cellules vs par permutations)

Regime #17066 : les deux occurrences d'« Interpretation des resultats » lisent
des sorties differentes (test SudokuCellsChromosome vs test
SudokuPermutationsChromosome) — retitrage distinctif, aucun texte modifie.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* fix(density,#17040): P16 — re-baseline parite jumelle apres redressement C#

Le redressement P16 retire 8 cellules de prose ajoutees par la campagne de
densite sur le cote C# des 4 paires Sudoku, sans toucher les jumeaux Python.
Les blob/content sha C# derivent donc, et `Twin parity audit (#8057)`
rougissait sur 4 paires qui etaient OK au base-ref origin/main.

Audit firsthand AVANT re-baseline (un --update aveugle consecrerait une
regression) : les 8 ids de cellule supprimes n'existent que dans des commits
de campagne, aucun n'est du contenu pre-campagne.
- 7 cellules (Sudoku-01 x1, Sudoku-03 x2, Sudoku-09 x4) ajoutees par
  d28e23e du 2026-09-14 (#16027, prose interpretative C#)
- 1 cellule (Sudoku-14 x1) ajoutee par 1f32e89 du 2026-09-03 (#14368)

Cote Python : recorded_python_sha == current_python_sha sur les 4 paires,
donc le jumeau Python n'a pas bouge. Le redressement annule exactement
l'enrichissement qui avait cause la derive.

Preuve : check_twin_parity.py --check rend [OK] sur les 4 paires apres update.
Le registre ne recoit que 4 enregistrements d'audit (SHA + date + auteur),
aucun notebook n'est modifie par ce commit.

Co-Authored-By: Claude Code <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: myia-po-2025 <po-2025@myia.local>